Skip to content

chore(mcp-compat): align CLI terminology with backend workspace rename (backend dd90d70..6ca3cc7) - #24

Open
ditto-mcp-maintainer[bot] wants to merge 1 commit into
mainfrom
mcp-maintenance/workspace-terminology-6ca3cc7
Open

chore(mcp-compat): align CLI terminology with backend workspace rename (backend dd90d70..6ca3cc7)#24
ditto-mcp-maintainer[bot] wants to merge 1 commit into
mainfrom
mcp-maintenance/workspace-terminology-6ca3cc7

Conversation

@ditto-mcp-maintainer

Copy link
Copy Markdown

Why

Backend MCP/server change in ditto-assistant/backend@6ca3cc7 (range
dd90d70..6ca3cc7) requires this repo to stay compatible.

Triggering backend change

The backend renamed 'knowledge graph' / 'graph' to 'workspace' across MCP
tool descriptions, error messages, and v5 API responses. Tool names
(create_dedicated_graph, list_knowledge_graphs, etc.) remain
unchanged, but all user-facing descriptions now use 'workspace' terminology.

What changed here

  • Updated CLI help text for --kg, knowledge-graphs, graph-sharing,
    graphs and all subcommands to use 'workspace' instead of 'graph'.
  • Updated README command reference and examples for consistency.
  • Updated test assertions that match help output strings.

Provenance

Opened by the Ditto MCP-extensions maintenance automation. Run state and prior
runs live in the dedicated mcp-extensions-maintainer knowledge graph and the
ditto-assistant/ditto-backend-ops-log ledger. A separate reviewer agent will
review this PR with fresh context.

Setup / migration notes

None. CLI command names and MCP tool names are unchanged; only descriptions
were updated.

Backend MCP/server surface changed 'graph' to 'workspace' in tool
descriptions and error messages. Update the CLI's user-facing help
text and README to stay consistent.

Refs: backend dd90d70..6ca3cc7
@ditto-mcp-maintainer

Copy link
Copy Markdown
Author

Verdict: LGTM with one nit.

  • Correctness: the CLI help-text and README changes accurately mirror the backend graphworkspace rename in MCP tool descriptions and v5 API error messages. Tool/endpoint names are unchanged, so no call-site breakage.
  • Scope: only user-facing strings were touched — no refactors or unrelated churn. Good discipline.
  • Tests: all 18 pass.
  • No secrets leaked.

Nit (non-blocking): the README usage-examples block near the top still shows [<@graph>...] and --subscribe <@graph> for the init command, but src/cli.ts was updated to [workspace...]. Align the README usage examples to workspace for consistency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants